Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat:semver #16

Merged
merged 1 commit into from
Sep 17, 2024
Merged

feat:semver #16

merged 1 commit into from
Sep 17, 2024

Conversation

JarbasAl
Copy link
Member

@JarbasAl JarbasAl commented Sep 17, 2024

Summary by CodeRabbit

  • New Features

    • Introduced a new workflow for automatic labeling of pull requests to enhance organization and tracking.
    • Added a workflow for publishing stable releases of Python packages, automating the release process.
    • Implemented a workflow to automate the release process and notify relevant channels upon merging pull requests.
  • Removed Features

    • Deleted multiple workflows related to publishing alpha, minor, and major releases, as well as merging from the dev branch to master, which may require manual intervention in the future.
    • Removed scripts for managing version increments for alpha, build, major, and minor versions, indicating a shift in version management strategy.

Copy link

coderabbitai bot commented Sep 17, 2024

Warning

Rate limit exceeded

@github-actions[bot] has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 28 minutes and 28 seconds before requesting another review.

How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

Commits

Files that changed from the base of the PR and between 3221343 and d08180b.

Walkthrough

The pull request introduces a new GitHub Actions workflow for automatic labeling of pull requests and removes several existing workflows related to publishing and version management. The new workflows, publish_stable.yml and release_workflow.yml, automate the processes for stable and alpha releases, respectively. Additionally, multiple scripts for version bumping and management have been deleted, indicating a shift in version control practices.

Changes

File(s) Change Summary
.github/workflows/conventional-label.yml Added: Workflow for automatic labeling of pull requests.
.github/workflows/dev2master.yml Removed: Workflow for merging dev branch into master.
.github/workflows/publish_alpha.yml Removed: Workflow for publishing alpha builds to PyPI.
.github/workflows/publish_build.yml Removed: Workflow for publishing builds to PyPI.
.github/workflows/publish_major.yml Removed: Workflow for publishing major releases to PyPI.
.github/workflows/publish_minor.yml Removed: Workflow for publishing minor releases to PyPI.
.github/workflows/publish_stable.yml Added: Workflow for publishing stable releases to PyPI.
.github/workflows/release_workflow.yml Added: Workflow for releasing software versions and notifying channels on PR merges.
scripts/bump_alpha.py Removed: Script for incrementing alpha version number.
scripts/bump_build.py Removed: Script for incrementing build version number.
scripts/bump_major.py Removed: Script for incrementing major version number.
scripts/bump_minor.py Removed: Script for incrementing minor version number.
scripts/remove_alpha.py Removed: Script for disabling alpha versioning.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant GitHub
    participant Workflow

    User->>GitHub: Opens PR
    GitHub->>Workflow: Trigger labeling workflow
    Workflow->>GitHub: Apply conventional labels
    GitHub->>User: Labels applied
Loading

🐰 In the meadow, changes abound,
New workflows sprout from the ground.
Scripts have hopped away with grace,
Stable releases now take their place.
Labels dance on PRs bright,
A joyful leap into the night! ✨


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    -- I pushed a fix in commit <commit_id>, please review it.
    -- Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    -- @coderabbitai generate unit testing code for this file.
    -- @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    -- @coderabbitai generate interesting stats about this repository and render them as a table.
    -- @coderabbitai read src/utils.ts and generate unit testing code.
    -- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    -- @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@JarbasAl JarbasAl merged commit dff5c6e into dev Sep 17, 2024
1 check passed
@JarbasAl JarbasAl deleted the semver branch September 17, 2024 12:52
@github-actions github-actions bot added feature and removed feature labels Sep 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant